http://blog.csdn.net/daquan198163/article/details/9304897 ZK入门指南 http://blog.csdn.net/daquan198163/article/details/11620641 ZK开发关键知识点 http://blog.csdn.net/daquan198163/article/details/17428495 Style定制与集成 http://blog.sina.com.cn/s/blog_94adc304010177bu.html ZK框架源代码分析 开发环境的搭建 https://www.zkoss.org/wiki/Small_Talks/2011/December/ZK_OSGi_-_Developing_plug-in_based_applications_with_OSGi

包说明

https://www.zkoss.org/wiki/ZK_Installation_Guide/ZK_Background/The_Content_of_ZK_Binary_Distribution Filename  Description  License  Shipped zcommon.jar  ZK's common library that ZK depends on (org.zkoss.*)  LGPL  All zweb.jar  ZK's Web library that ZK depends on (org.zkoss.web.*  LGPL  All zk.jar  ZK core functions, such as ZK Loader and Update Engine. (org.zkoss.zk.*)  LGPL  All zul.jar  ZUL components (org.zkoss.zul.*)  LGPL  All zhtml.jar  ZK HTML (ZHTML) components (org.zkoss.zhtml.*)  LGPL  All zkbind.jar  ZK Bind, including data binding and MVVM.  LGPL  All zkplus.jar  ZK extra utilities integrated easily with other frameworks. (org.zkoss.zkplus.*)  LGPL  All zel.jar  ZK's implementation of EL 2.2. It is based on Apache Tomcat 7's EL 2.2 implementation.  Apache  All zkex.jar  ZK professional ZUL components and utilities (org.zkoss.zkex.*)  Commercial  ZK PE and EE only zml.jar  ZK XML components for generating XML output (org.zkoss.zml.*)  Commercial  ZK PE and EE only zkmax.jar  ZK enterprise components and utilities (org.zkoss.*)  Commercial  ZK EE only 这是id的某个版本的使用jar情况，当然ckez.jar是单独打包的。 zcommon_8.0.2.2.jar zel_8.0.2.2.jar zhtml_8.0.2.2.jar zjavassist_8.0.2.2.jar：这个需要javassist的zk版本，参考：[官方链接](https://github.com/zkoss/zk/blob/884e074c3ab999798dcf38b01564ec1f4c940818/bin/zjavassist) zk_8.0.2.2.jar zkbind_8.0.2.2.jar zkplus_8.0.2.2.jar zul_8.0.2.2.jar zweb_8.0.2.2.jar

hello world

http://www.cnblogs.com/damonhuang/archive/2013/06/01/3113004.html http://www.cnblogs.com/damonhuang/archive/2013/06/02/3113698.html

MVC

http://www.cnblogs.com/damonhuang/archive/2013/06/01/3113128.html

MVMM

http://www.cnblogs.com/damonhuang/archive/2013/06/02/3114387.html

Client or Server Implementation

For each function like add or archive todo, you need to determine whether to implement it on the client or server-side. Both ways have its pros and cons. In general, we recommend implementing on the server-side, the reasons are: An application logic might involve a lot of data from different parts of a system; it is, therefore, easier to access them on the server-side. To implement such functions on the client-side, you would have to push all the data to the client-side first. Avoid exposing business logic to users. For a complicated business logic, Java has better compiler checking. If a page is accidentally closed or reloaded, the data that have not been synchronized with a server will be lost. Meanwhile, the server-side implementation will increase the network traffic and requires more execution time (at least a round-trip from a client to server). Therefore, if it's critical to have a fast response time for your application, you can choose a client-side implementation. Take, for example, "archive" function. The potential problem might be the re-rendering performance when the number of items is very large. You can implement it with Javascript and invoke a command with those removed todos' index as a parameter to avoid re-rendering the whole list. Then you would just have to implement logic removal on the server side. https://www.zkoss.org/wiki/Small%20Talks/2016/May/Integrating%20ZK%20with%20AngularJS